WIP Revisit Kustomize and Galera setup with MariaDB 10.5 #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
solsson
changed the title
solsson
added a commit
to Yolean/kubernetes-keycloakx
that referenced
this pull request
Dec 23, 2020
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The answer to the question in 7136118 is that we can't refer to the parent folder as base, hence the eternally out-of-date variants (they can't be up to date when using a commit ref, and would be unreliable without a ref).
I'm also interested in if Galera config step can be simplified now, given that our initial setup was done back in 2016 when no one (but us) would try to run a database in Kubernetes.